The Microsoft Configuration Manager 2007 Management Pack for Operations Manager 2007 provides proactive monitoring of your Microsoft System Center Configuration Manager 2007 environment. This management pack includes:

Before you install the Configuration Manager 2007 Management Pack, read the Configuration Manager 2007 User's Guide. The guide includes the instructions you need to correctly deploy, configure and use the management pack and known issues for the management pack.

System Requirements

The only supported operating systems for the Configuration Manager 2007 Management Pack is the Windows Server 2003 operating system.

Software Requirements

The Configuration Manager 2007 Management Pack requires Microsoft System Center Operations Manager 2007 be installed on the machine running the management pack.

The Operations Manager 2007 MOM 2005 Backward Compatibility MP Update must be installed before installing the Configuration Manager 2007 Management Pack. For more information about the Operations Manager 2007 MOM 2005 Backward Compatibility MP Update, visit the download Web site (http://go.microsoft.com/fwlink/?LinkId=101878).

Known Issues

The following section provides information about known issues with the Configuration Manager 2007 Management Pack:

Rules with Repeat Counters Do Not Fire Proper When Repeat Counters Are Exceeded

The following rules with repeat counters do not fire properly when the repeat count is exceeded:

  • ConfigMgr 2007 Status: Management Point's File Dispatch Manager could not connect to Site Server
  • ConfigMgr 2007 Status: Management Point encountered a database connection error
  • ConfigMgr 2007 Status: CI Assignment Manager failed to process CI Assignment changes
  • ConfigMgr 2007 Status: CI Assignment Manager failed to process a CI Assignment but will retry on next processing cycle

64-Bit Operations Manager Agent Not Support on Configuration Manager Clients and Servers

64 bit Configuration Manager 2007 servers and clients cannot be monitored by the 64-bit Operations Manager 2007 client.

Workaround

Install the 32-bit Operations Manager client on the 64-bit Configuration Manager 2007 server or client to monitor Configuration Manager 2007 functionality. The 64-bit agent, if installed, must be uninstalled either manually or from the Administration console before installing the 32-bit agent.

SMS 2003 and Configuration Manager 2007 Consoles Cannot Be Run from the Same Operations Manager Machine

Operations Manager 2007 cannot launch both Systems Management Server (SMS) 2003 and Configuration Manager 2007 from the same machine. The more recently installed program will launch when the Action is initiated in the Operations Manager 2007 console.

Workaround

Install SMS 2003 and Configuration Manager 2007 on separate Operations Manager 2007 machines to be able to launch their consoles from the Operations Manager console.

Operations Manager Agent Paused During Configuration Manager 2007 Software Updates

The Configuration Manager 2007 software updates manager will place the Operations Manager 2007 agent in maintenance mode while software updates are being applied even if the Disable Operations Manager Alerts while this program runs check box is not checked in the Software Update Deployment Package properties. Administrators might not be alerted that the Operations Manager 2007 agent is in maintenance mode.

Workaround

None. The Operations Manager 2007 agent will leave maintenance mode when software updates are complete and resume normal monitoring.

Duplicates Appear in the Site Hierarchy Health Explorer

The Site Hierarchy Health Explorer does not accurately portray the site hierarchy relationships. Grandchild sites are discovered and portrayed as child sites. These sites should not be discovered by the grandparent site, but only by the parent site. This results in duplicates in the Site Hierarchy Health Explorer.

Workaround

Navigate through the site hierarchy in the Site Hierarchy Health Explorer to accurately view the hierarchy of the sites.

Additional Objects Appear in Public Views

The following objects will appear in public views:

  • Database Requests processed in the last 24 hours
  • Inbox ciamgr.box Backlog in the last 48 hours
  • Inbox objmgr.box/INCOMING Backlog in the last 48 hours
  • Inbox objmgr.box/INCOMING/Retry Backlog in the last 48 hours
  • PXE Requests processed in the last 24 hours
  • PXE Requests processed/second in the last 24 hours
  • DHCP Discover Requests processed in the last 24 hours
  • DHCP Discover Requests processed/second in the last 24 hours
  • Total Requests in the last 24 hours
  • Total Requests/second in the last 24 hours

Workaround

None.

Changes

Section last updated—February 2008

The following changes and corrections have been added for the February 2008 release of the management pack:

  1. Scripts now support connection to a Configuration Manager 2007 site server where the database resides on a named instance of SQL database server.
  2. The following performance threshold rules were changed from monitoring averages to monitoring the change in the performance counter. This allows the rule to more accurately reflect changes of interest.
    • PSP Total Requests > 10,000 over 1 hour
    • PSP PXE Requests processed > 4000 over 1 hour
    • PSP Database Requests processed > 4000 over 1 hour
    • PSP DHCP Discover Requests processed > 8000 over 1 hour
    • PSP Total Failed Requests > 10 over 30 minutes
  3. The style for the non-containment line in the site hierarchy diagram was changed from solid line to dash-dot-dot. This simplifies distinguishing between containment and non-containment (site server to site system) lines.
  4. The State Message Summary Task status is now correctly being interpreted as the number of rows processed and not simply an error code. If the value is greater than or equal to zero, the task completed successfully. If the value is less than zero, the task failed. A critical alert is now raised upon failure and not when some rows are successfully processed.